Secure NCSA Mosaic and Secure NCSA httpd

To: www-security@ns1.rutgers.edu
Subject: Secure NCSA Mosaic and Secure NCSA httpd
From: wtwong@eit.com (William Tao-Yang Wong)
Date: Mon, 14 Nov 1994 14:52:50 -0500
Reply-To: wtwong@eit.com (William Tao-Yang Wong)
   I am resending this to the list, for some reason this message ended up
at,
	owner-www-security@nsmx.rutgers.edu

rather than

	www-security@nsmx.rutgers.edu

Appologies to the original sender.

Simon.
------------------------------------------------------------------------------
Received: from eitech.eit.com (root@eitech.eit.COM [192.100.58.2]) by ns1.rutgers.edu (8.6.8.1+bestmx+oldruq/8.6.6) with SMTP id VAA12895 for <www-security@ns1.rutgers.edu>; Fri, 11 Nov 1994 21:36:48 -0500
Received: from pacific.eit.com by eitech.eit.com (4.1/SMI-4.1)
	id AA14775; Fri, 11 Nov 94 18:36:14 PST
Date: Fri, 11 Nov 94 18:36:14 PST
From: wtwong@eit.COM (William Tao-Yang Wong)
Message-Id: <9411120236.AA14775@eitech.eit.com>
Received: by pacific.eit.com (4.1/SMI-4.1)
	id AA16825; Fri, 11 Nov 94 18:36:23 PST
To: shttp-talk@openmarket.com, www-security@ns1.rutgers.edu
Subject: Secure NCSA Mosaic and Secure NCSA httpd

Perhaps, this might help to clarify the status of Secure HyperText Transfer
Protocol reference implementations.

1. Who owns Secure HyperText Transfer Protocol? 

The Secure HyperText Transfer Protocol specification is non-proprietary.
The developers of S-HTTP are working with the standards committees to
evolve the specification into a standard. 

The first reference implementations of S-HTTP include licensed material
>From Enterprise Integration Technologies, RSA Data Security, Inc., and the 
National Center for Supercomputing Applications at the University of
Illinois, Urbana-Champaign. 

EIT encourages other parties to create independent client and server
implementations that support the S-HTTP protocol. 

2. Where can I obtain a copy of a WWW client and/or server which supports
S-HTTP? 

Based on NCSA's license agreements with EIT, EIT may only distribute the
reference implementation, which incorporates NCSA Mosaic, to
CommerceNet participants. CommerceNet sponsoring members have access
to the client and server reference implementations. CommerceNet associate
members have access to the client reference implementation. Additional
client and server licenses will be allocated to CommerceNet use on a
per-need basis and subject to CommerceNet Sponsors Steering Committee
approval. 

EIT has in return agreed to license its security enhancements in the Secure
NCSA Mosaic World-Wide Web client to NCSA. These enhancements may
be redistributed at NCSA's discretion under their non-commercial terms
subject to the United States export control laws. However, NCSA is under no
obligation to release the security enhancements to the Mosaic World-Wide
Web client. 

There is a commercial vendor of Secure HTTP implementation toolkits, and
we expect to see commercial WWW client and server vendors adopt S-HTTP
and make such capabilities available in their clients and servers soon. 

For further information, send mail to shttp-info@eit.com and
info@terisa.com. For a copy of the Secure HTTP specification, send mail to
shttp-info@commerce.net. 

Regards,
William

-------------------------------------------------------------------------------
William T. Wong                                 wtwong@eit.com
Enterprise Integration Technologies             Phone: 415-617-8011
800 El Camino Real			        Fax:   415-617-8019
Menlo Park, CA 94025				http://www.eit.com/